-
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supporting of M:N relation (many type of messages in many channels) required #224
Supporting of M:N relation (many type of messages in many channels) required #224
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #224 +/- ##
============================================
- Coverage 84.65% 84.18% -0.47%
+ Complexity 372 365 -7
============================================
Files 47 48 +1
Lines 1088 1075 -13
============================================
- Hits 921 905 -16
- Misses 167 170 +3 ☔ View full report in Codecov by Sentry. |
Hi @holdmann! Thank you for investigation and your code. |
…ring_of_many_channels_many_type_of_messages
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need any changes in docs?
@samdark no, it's just a bugfix |
I've found the bug and reproduced it in tests. Thank you for your work. |
Any queue can has many channels, each of them also can has many types of messages.
Current realization supports only one channel <-> one type of message relation.
Еherefore, when processing a queue messages, they are processed successfully until a message with a different type is received.
Then it throws exception:
The main problem is here:
src/Middleware/Consume/ConsumeMiddlewareDispatcher.php on line 43
As you can see
stack
be onlynull|MiddlewareConsumeStack
, instead of it should beMiddlewareConsumeStack[]
.Additional info